Profile-enabled dynamic runtime environment for web application servers

ABSTRACT

Techniques are disclosed for allowing administrators to manage runtime environments (RTEs). An RTE configuration component prompts for metadata characterizing a plurality of dynamically configurable runtime environments (RTE) for executing data queries. The RTE configuration component generates an RTE definition to associate with each of the plurality of RTEs. When a query is received for execution, the RTE configuration component dynamically configures the server computing system for query execution according to a selected one of the plurality of RTE definitions.

BACKGROUND

Field

Embodiments of the invention generally relate to techniques for accessing data in computing applications. More specifically, techniques are disclosed for switching runtime data environments.

Description of the Related Art

Business and government entities frequently have different data sets for different sectors of their business. That is, businesses often own multiple databases containing different sets of data (known as “data environments” or “libraries”) that are similar in format, wherein each library is populated with a distinct set of data. Thus, the format of the data environment is similar in column and row structure, heading structure, and the like. However, these data environments may be isolated from one another such that a user who is currently accessing one data environment cannot easily switch to accessing another data environment.

Consider the following example: the Minnesota state government records data about traffic violations for each county in isolated libraries. Thus, a state employee for Olmsted County has access to the data environment for traffic violations in Olmsted County. However, if the state employee wishes to access traffic violation data for a different county, such as Ramsey County, the state employee cannot easily gain access to the Ramsey County library since the libraries are isolated. In order to access the Ramsey County library, the Olmsted County employee may have to take additional steps, such as logging out of the traffic violation software and logging back in as a Ramsey County employee, or requesting that a network administrator restart and reload the Olmsted county server with the data libraries for Ramsey County.

A similar problem occurs in multi-tenant applications. A multi-tenant application is a single running instance of a program with multiple users simultaneously using the program. Oftentimes, a multi-tenant application uses multiple servers in order to isolate one tenant's data from another. Thus, one tenant cannot access another tenant's data servers without reloading or restarting one or more of the servers or setting up multiple instances of the multi-tenant application.

Another example of isolated data sets occurs when a cloud service provider hosts data environments for several clients in a common data center. In this example, each client's data is hosted on a separate virtual machine. A virtual machine effectively divides the resources of one computer amongst many users by simulating hardware components. An entire server can be virtualized in this manner, allowing several clients to share the resources of a single server without the knowledge that other clients are also using the server. Oftentimes, a client will duplicate data environments on multiple virtual machines in order to ensure isolation.

A third example of isolated data environments occurs with web-based server applications. One instance of this is a business analytics tool that allows a user to execute queries on a runtime environment (RTE). Running a report involves, for example, accessing sales data stored in the database and generating a visual representation of that sales data, such as a spreadsheet or pie chart of sales numbers. For example, a business stores sales data for all the countries in which sales have been made in isolated environments, one environment for each country. In this example, an associate salesperson is limited to access for US sales data due to her associate status, but she is not be allowed access to sales data for Canada. The associate salesperson is then promoted to regional manager, and is thus granted access to all sales data worldwide. However, due to the isolated nature of the data environments for each country, the new regional manager cannot easily switch from running reports for US sales to running reports for Canadian sales. Thus, the regional manager may need to log out as a US salesperson and log in as a Canadian salesperson. Alternatively, the regional manager may need to request that the US sales data server is restarted and reloaded with Canadian data.

SUMMARY

Embodiments presented herein include a method for managing runtime environments (RTEs). The method may generally include receiving metadata characterizing multiple dynamically configurable RTEs for executing data queries. The method may also generally include generating an RTE definition to associate with each of the RTEs. The method may also generally include, dynamically configuring the server computing system for query execution according to selected RTE definitions.

Other embodiments include, without limitation, a computer-readable medium that includes instructions that enable a processing unit to implement one or more aspects of the disclosed methods as well as a system having a processor, memory, and application programs configured to implement one or more aspects of the disclosed methods.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 illustrates an example computing infrastructure including a client and a server computer, according to one embodiment of the invention.

FIG. 2 illustrates an example embodiment of a web query application, according to one embodiment of the invention.

FIGS. 3A and 3B illustrate a method for executing a query that allows a user to switch runtime environments, according to one embodiment of the invention.

FIG. 4 illustrates a method for managing and editing a runtime environment for the runtime configuration component, according to one embodiment of the invention.

FIG. 5 illustrates a method for associating user profiles and/or group profiles with a runtime environment for the runtime configuration component, according to one embodiment of the invention.

FIG. 6 illustrates an example interface showing a generated report of sales data.

FIG. 7 illustrates an example computing system configured to execute queries and manage profiles.

DETAILED DESCRIPTION

Embodiments presented herein provide techniques allowing users to access multiple runtime environments (RTEs) from a web browser hosted by a client device. An RTE, as used herein, includes a set of data libraries (“libraries”). The techniques disclosed herein allow users to access libraries contained in multiple, isolated RTEs through an application. That is, a user with access to data libraries associated with a first RTE can access data libraries associated with a second RTE, without reloading the server containing the RTE, or logging in as a different user. One example of an application in which users may access libraries is a web query application. Further, in cases where the data libraries store different data in a common format, the same query tool (and queries) can run over either library. In one embodiment, as part of query execution, the web query application determines an RTE to use for each query submitted by a user interacting with a web client. Alternatively, the user specifies the correct RTE for the query sent by the user.

In one embodiment, a user profile identifies which RTEs a user is authorized to access. Consider a company which sells equipment around the globe. Assume the company maintains sales data for each country in which the company does business. In this example, a salesperson uses a web browser which hosts data libraries for the RTE associated with sales made in the US. However, the salesperson would like to access sales data for Canada. Further, assume the corresponding user profile authorizes the salesperson to access all RTEs associated with countries in North America. When the salesperson submits a query requesting Canadian sales data, the web application determines that the Canadian RTE needs to be accessed. In response, the computer server configures the data libraries accessed by the query to correspond to the Canadian RTE. The web query application returns Canadian sales data to the salesperson. Alternatively, the salesperson may actively select the Canadian RTE (from, e.g., a drop-down menu). In such a case, the query application (after validating the user's authority to access this RTE) executes a query against the Canadian RTE.

In one embodiment, the web query application determines which RTE to configure each time a user submits a query. If the user submits a query against an RTE that is currently configured, the web query application does not reconfigure a new RTE. Rather, the web query application executes the query against the libraries associated with the currently configured RTE. In contrast, if the user submits a query against an RTE that is not currently configured, the web query application executes the query as described above.

Embodiments presented herein provide techniques for allowing an administrator to assign profiles to RTEs. The techniques disclosed herein allow an administrator to associate a specific user profile with an RTE and/or associate a group profile with an RTE. A group profile may be associated with multiple users and an RTE. Continuing with the above example, assume the company employs both junior and senior salespeople. In this example, junior salespeople might access North America sales data. An administrator can create a “junior group profile” that allows junior salespeople to access RTEs associated with North American sales. Thus, the junior group profile would be associated with RTEs for Canada, the US and Mexico. In such a case, the web query application would limit access to any of the data libraries for Canada, the US and Mexico to members of the junior group profile.

Other embodiments presented herein provide techniques for allowing an administrator to manage and edit RTEs. The techniques allow an administrator to add, remove, change or copy RTEs associated with specific user profiles or group profiles. In addition, the properties of one or more RTEs may be edited by an administrator. Also, embodiments are described herein using a web query application as a reference example of an application configured to access a database system which dynamically configures a runtime environment on a per-query basis. Of course, embodiments of the invention may be adapted for a variety of applications programs configured to access database systems.

FIG. 1 illustrates an example computing infrastructure 100, including client computer 102 and server computer 104, according to one embodiment of the invention. The computing infrastructure 100 allows a user to execute a query (such as query 108) against multiple RTEs. As shown, client computer 102 hosts a web browser 104. Web browser 104 is configured to execute runtime environment 106. A user of client computer 102 sends a query 108 to server computer 112 through network 110. Server computer 112 may be a physical computing system (e.g., a system in a data center) or may be a virtual computing instance executing within a computing cloud. As shown, server computer 112 stores RTE definitions 114, RTE configuration component 116, and web query application 118. Server computer 112 also stores profiles 120 and libraries 122. RTE definitions 114 stores data about each RTE that may be exposed to a client interaction with a web query application. Each RTE may specify a group of data libraries that are associated with that RTE. As noted, each RTE may store data using a similar format or schema, but store different actual data. For example, an organization may include the same type of sales data for each region, using the same storage format. Thus a query application used to access data according to that format can access data from the RTE from any region. RTE configuration component 116 allows an administrator to edit RTE definitions 114 and profiles 120. This process is described in greater detail in the detailed description associated with FIGS. 4 and 5. Web query application 118 receives query 108 from client computer 102 and executes query 108 against a set of the libraries 122. RTE libraries 122 store data associated with each RTE in RTE definitions 114. In one embodiment, exit programs 124 may be called by web query application 118 in order to perform additional functions (e.g., modify user searches to become case insensitive searches, or track data from the data libraries accessed by the user). Exit programs 124 access data stored in exit program libraries 126.

In one embodiment, web query application 118 determines which RTE, and thus, which library 122, query 108 is executed against. Furthermore, web query application 118 determines the RTE by evaluating profiles 120. Alternatively, the user may identify an RTE when submitting query 108. In both cases, web query application 118 executes query 108 against the libraries 122 associated with the determined RTE.

FIG. 2 illustrates an example of the web query application 118, according to one embodiment. As shown, web query application 118 accesses three “master tables,” including active RTE user table 202, user RTE table 208, and RTE definition table 214. Active RTE user table 202 identifies RTEs defined for the server computer 112. In this example, active RTE user table 202 includes RTE ID 204 and RTE username 206. RTE username 206 is the name of a user with access to the currently configured RTE specified by RTE ID 204. The currently configured RTE may be the RTE currently running on client computer 102 (i.e., RTE 106).

User RTE table 208 associates users with specific RTEs. User RTE table 208 includes RTE ID 210 and RTE username 212. While user RTE table 208 is illustrated using one RTE ID and one RTE username, user RTE table 208 may of course store multiple RTE IDs 210 and RTE usernames 212.

RTE definition table 214 describes the runtime setup for each RTE available on server computer 112. In this example, RTE definition table 214 stores the following RTE definitions: RTE ID 216, RTE username 218, RTE description 220, and the location of RTE libraries 222. RTE definition table 214 stores one such set of RTE definitions for each RTE available on server computer 112.

In a further embodiment, RTE definition table 214 stores two additional RTE definitions: RTE exit programs 224 and RTE exit program libraries 226. RTE exit program 224 references exit programs 124 associated with RTE ID 216. Similarly, RTE exit program library 226 references RTE libraries 126 associated with RTE exit program 224.

In one embodiment, each time web query application 118 services a query made by a user (such as query 108), web query application 118 determines which libraries to execute query 108 against. More specifically, web query application 118 reads the active RTE user table 202 to identify a user profile associated with the query. That is, web query application 118 reads RTE username 206 to identify the user. Furthermore, web query application 118 determines whether query 108 references the currently configured RTE (i.e., whether query 108 references RTE ID 204). If query 108 references the currently configured RTE, the web query application 118 executes query 108 against the currently configured RTE (i.e., against the data libraries associated with RTE ID 204). That is, web query application 118 does not reconfigure the library associated with the currently configured RTE if query 108 references the currently configured RTE. Instead, the appropriate runtime definitions are already loaded, as indicated by the arrows between active RTE table 202 and RTE definition table 214. In one example, active RTE table 202 and RTE definition table 214 are relational database tables. In this example, two elements from active RTE table 202 are joined with two elements from RTE definition table 214 (i.e., RTE ID 204 is joined with RTE ID 216, and RTE username 206 is joined with RTE username 218).

If query 108 does not reference the currently configured RTE, then web query application 118 determines an unconfigured RTE against which to execute query 108. For example, assume web browser 104 submits a query to run a report against an RTE other than the currently configured one (referred to as an ‘unconfigured’ RTE). In response, web query application 118 reads active RTE user table 202 and the profile for the user of client computer 102. That is, web query application 118 retrieves RTE ID 204 and RTE username 206. Then, web query application 118 identifies user profiles that match the user from RTE table 208.

If web query application 118 does not find a matching profile, a default profile may be selected, or an error message may be sent to the user. If web query application 118 finds a matching profile in user RTE table 208, web query application 118 proceeds to configure an RTE other than the currently configured RTE as described below.

Web query application 118 searches for profiles in user RTE table 208. Web query application 118 matches an RTE username 206 (i.e., the username of client computer 102) with an RTE username from user RTE table 208. In this case, web query application 118 finds a matching profile by locating RTE username 212 and associated RTE ID 210. RTE ID 210 is the identification of an unconfigured RTE. The RTE definitions for the unconfigured RTE are stored in RTE definition table 214. To change the currently configured RTE (i.e., to configure a new RTE), web query application 118 locates the RTE definitions associated with RTE ID 210 from RTE definition table 214. Server computer 112 then sends the defined runtime associated with RTE ID 210 to client 102. Note, the RTE definitions associated with RTE ID 210 include RTE libraries 222, and RTE libraries 222 are associated with one of the unconfigured RTEs, as shown by the arrows between user RTE table 208 and RTE definition table 214. In one example, the arrows denote joined elements in two relational databases. In this example, the first relational database table is user RTE table 202 and the second relational database table is RTE definition table 214. Furthermore, the elements being joined are RTE ID 210 with RTE ID 216, and RTE username 212 with RTE username 218.

In a further embodiment, web query application 118 also references exit program 124 using the location specified by RTE exit program 224. In addition, web query application 118 also references and exit program libraries 126 using RTE exit program library 226. Next, web query application 118 changes the libraries associated with RTE ID 204 (i.e., the currently configured RTE) with the data libraries associated with RTE ID 210 (i.e., an unconfigured RTE). More specifically, web query application 118 links RTE description 220, RTE libraries 222, and optionally, RTE exit program 224 and RTE exit program libraries 226. Linking, in turn, allows a user to access data from the RTE libraries 222 associated with a previously unconfigured RTE. At this point, RTE configuration is complete. That is, the RTE associated with RTE ID 210 (the unconfigured RTE) is now the currently configured RTE. Finally, web query application 118 then executes query 108 on the data libraries associated with RTE ID 210.

In some cases, the user of client computer 102 selects which RTE to execute a query against. For example, a user may select the RTE using a drop-down menu in web browser 104 and selecting a desired RTE. In this case, the user selects an RTE from web browser 104 and sends a query to server computer 112.

If no matching RTE username is found, a default username may be selected or an error message may be sent to an administrator. If a matching RTE username is found, the runtime definitions associated with the matching RTE username are loaded in the manner described above.

An administrator may manage RTEs with RTE configuration component 116. To add an RTE, the administrator updates user RTE table 208 and RTE definition table 214. The master tables may be modified without ending web query application 118 and without requiring the user to log out of the current RTE or to reload the server with another RTE.

FIGS. 3A and 3B illustrate a method 300 for executing a query that allows a user to switch runtime environments, according to one embodiment of the invention. Although the method steps are described in conjunction with FIG. 1, persons skilled in the art will understand that any system configured to perform the method steps, in any order, falls within the scope of the present invention. The method begins at step 302, where web query application 118 receives a query 108 and a user ID. At step 304, web query application 118 identifies the user based on the user ID. At step 306, web query application 118 identifies user profiles and/or group profiles associated with the user. If more than one profile is identified, the method continues in FIG. 3B with step 352.

Otherwise, at step 312, web query application 118 determines and retrieves an RTE associated with the selected profile. At step 314, web query application 118 changes the libraries associated with RTE 106 to the libraries associated with the configured RTE from libraries 122. Note, if the RTE identified at 312 is currently configured, the system need not reconfigure it. At step 318, web query application 118 executes query 108 against the configured RTE. Optionally, at step 316, web query application 118 executes an exit program for the configured RTE.

FIG. 3B illustrates a method 350 selecting an RTE profile. At step 352, web query application 118 determines whether a specific profile is associated with the user. If so, then, at step 354, web query application 118 selects the specific user profile and the method returns to step 312. If there is no specific user profile associated with the user, then, at step 356, web query application 118 determines whether there is a group profile associated with the user. If so, web query application 118 selects the group profile and the method returns to step 312. If there is no group profile, then, at step 360, web query application 118 selects a default profile and the method returns to step 312. If no default profile is available, then an error-handling routine may be called to display an error to the user of client computer 102 and/or notify the administrator of RTE configuration component 116.

FIG. 4 illustrates a method for dynamically adding, removing, changing or copying a runtime environment for runtime configuration component 116, according to one embodiment of the invention. Although the method steps are described in conjunction with FIG. 1, persons skilled in the art will understand that any system configured to perform the method steps, in any order, falls within the scope of the present invention. The method 400 begins at step 402, in which RTE configuration component 116 prompts for the following metadata: an RTE name, RTE description, and RTE libraries. At step 406, RTE configuration component 116 generates an RTE definition with the RTE name and RTE description from step 402. At step 408, RTE configuration component 116 associates RTE libraries from step 402 with the generated RTE. At step 410, RTE configuration component 116 associates the RTE exit program and the RTE exit program library from step 402 with the generated RTE. Optionally at step 402, RTE configuration component 116 prompts for additional metadata, including: an RTE exit program and RTE exit program libraries. Optionally, at step 404, RTE configuration component 116 copies or deletes one or more RTEs.

FIG. 5 illustrates a method for associating user profiles and/or group profiles with a runtime environment for the runtime configuration component, according to one embodiment of the invention. Although the method steps are described in conjunction with FIG. 1, persons skilled in the art will understand that any system configured to perform the method steps, in any order, falls within the scope of the present invention. The method 500 begins at step 502, in which RTE configuration component 116 associates a user profile from profiles 120 with an RTE from RTE definitions 114. Optionally, at step 504, RTE configuration component 116 associates a group profile from profiles 120 with an RTE from RTE definitions 114.

FIG. 6 illustrates an example interface showing a generated report of sales data. As shown, interface 600 allows a user to access data against dynamically configured RTEs. In one embodiment, interface 600 is web browser 104. Interface 600 displays sales data from Eastern Canada and the Eastern US. Each region contains a sample store (i.e., store “ABC” and store “XYZ”), and the sales numbers associated with these sample stores over the course of two years. Using the sales example described earlier, a user of client computer 102 can execute queries on multiple RTEs, wherein each RTE is associated with a different country in North America. Thus, the user can run reports against isolated RTEs for Canada, Mexico and the US without logging in and out as a different user, or having to reload computer server 112 with different data (e.g., reloading computer server with a different set of data libraries for libraries 122. As shown in FIG. 6, data for Store ABC, located in Eastern Canada, populates the ‘Year 1’ and ‘Year 2’ columns. In the same window, data for Store XYZ, located in the Eastern US, populates the same columns, allowing a side-by-side comparison of data from two isolated RTEs.

FIG. 7 illustrates an example computing system 700 configured to execute queries and manage profiles. As shown, the computing system 700 includes, without limitation, a central processing unit (CPU) 702, a memory 704, a bus 714, storage 708, and network interface 716. Further, in the context of this disclosure, the computing elements in computing system 700 may correspond to a physical computing system (e.g., a system in a data center) or may be a virtual computing instance executing within a computing cloud.

The CPU 702 retrieves and executes programming instructions stored in memory 704 as well as stores and retrieves application data residing in memory 704. The bus 714 is used to transmit programming instructions and application data between CPU 702, memory 704, storage 708 and network interface 716. Note, CPU 702 is included to be representative of a single CPU, multiple CPUs, a single CPU having multiple cores, and the like. Furthermore, memory 704 is generally included to be representative of a random access memory. Storage 708 may be a disk drive storage device or solid state storage device. Although shown as a single unit, storage 708 may be a combination of fixed and/or removable storage devices, such as fixed disc drives, removable memory cards, or optical storage, network attached storage (NAS), or a storage area-network (SAN). Storage 708 stores profiles 120 and libraries 122.

Illustratively, memory 704 includes RTE configuration component 116, web query application 118, and RTE definitions 114. RTE configuration component 116 allows an administrator to manage user profiles 120. Web query application 118 executes queries (such as query 108) submitted by the user of client computer 102. RTE definitions 114 stores the locations of data (such as data found in libraries 122) associated with RTEs (such as RTE 106).

Web query application 118 executes queries against multiple RTEs and return data from libraries 122 to client computer 102. Thus, client computer 102 may display data from multiple, isolated RTEs without requiring the user to log in and out as a different user, or restart and/or reload server computer 112. For example, client computer 102 may run web browser 104. Web browser 104 may contain RTE 106, which is associated with US sales data, as illustrated in FIG. 6. The user of client computer 102 may send query 108 in order to run a report on Canadian sales data. Web query application 118 executes the query and returns the requested data from libraries 122 data to client computer 102. Thus, the data fields in web browser 104 are populated with data from the library associated with the Canadian sales data RTE, as shown in FIG. 6. In this manner, web query application 118 allows client computer 102 to display data from two separate RTEs simultaneously.

The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Aspects of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

Embodiments of the invention may be provided to end users through a cloud computing infrastructure. Cloud computing generally refers to the provision of scalable computing resources as a service over a network. More formally, cloud computing may be defined as a computing capability that provides an abstraction between the computing resource and its underlying technical architecture (e.g., servers, storage, networks), enabling convenient, on-demand network access to a shared pool of configurable computing resources that can be rapidly provisioned and released with minimal management effort or service provider interaction. Thus, cloud computing allows a user to access virtual computing resources (e.g., storage, data, applications, and even complete virtualized computing systems) in “the cloud,” without regard for the underlying physical systems (or locations of those systems) used to provide the computing resources.

Typically, cloud computing resources are provided to a user on a pay-per-use basis, where users are charged only for the computing resources actually used (e.g. an amount of storage space consumed by a user or a number of virtualized systems instantiated by the user). A user can access any of the resources that reside in the cloud at any time, and from anywhere across the Internet. In context of the present invention, a user may access a cloud-based web query application in order to submit queries against multiple RTEs, which can also be stored in the cloud. For example, a client computer could send queries which are then executed by a web query application on a computing system in the cloud. Further, the web query application could retrieve data from libraries stored in the cloud computing system. Doing so allows the data retrieved to be displayed in an RTE on the client computer.

As described, embodiments presented herein provide techniques for allowing users to access multiple RTEs from a web browser hosted by a client device. Advantageously, this approach allows for a user to access isolated data libraries from multiple RTEs without logging out and logging back in as a different user, restarting or reloading a computer server, or creating new virtual machines to host isolated data libraries.

Additional embodiments presented herein provide techniques for allowing administrators to manage and edit RTEs, as well as allowing administrators to associate users with RTEs. Advantageously, this approach allows for administrators to manage and edit RTEs as well as modify user access to RTEs while RTEs are currently running (i.e., without shutting down the server configured to run RTEs).

While the foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow. 

What is claimed is:
 1. A computer-readable storage medium storing instructions executable to perform an operation to manage runtime environments (RTEs), the operation comprising: receiving, by a server computing system, a set of runtime environment (RTE) properties characterizing a plurality of dynamically configurable RTEs for executing data queries, wherein each of the plurality of dynamically configurable RTEs corresponds to a respective set of data libraries from a plurality of sets of data libraries, wherein each set of data libraries is distinct and stores data according to a predefined schema common across the plurality of RTEs, wherein each set of data libraries is isolated by being hosted on a respective, distinct virtual machine, wherein a respective RTE definition is generated to associate with each of the plurality of RTEs; upon receiving a query from a requesting entity logged in via a current virtual machine, dynamically determining one of the plurality of RTEs to execute the query against, wherein the RTE is determined based on a profile corresponding to the requesting entity, wherein the profile is selected from a user profile and a group profile, wherein the determined RTE is associated with one or more exit programs and one or more exit program libraries; upon determining that the server computing system is currently configured to access the set of data libraries corresponding to a given one, of the plurality of RTEs, that does not match the determined RTE, dynamically reconfiguring the server computing system to access the set of data libraries corresponding to the determined RTE, wherein the server computing system is dynamically reconfigured by operation of at least one computer processor without requiring any server restart and without requiring any logging in via a different virtual machine than the current virtual machine; and prior to executing the query against the set of data libraries corresponding to the determined RTE, dynamically modifying the query using the one or more exit programs and the one or more exit program libraries associated with the determined RTE, wherein the dynamically modified query is executed against the set of data libraries corresponding to the determined RTE on the dynamically reconfigured server computing system in order to generate a set of results that is output to the requesting entity.
 2. The computer readable storage medium of claim 1, wherein the set of RTE properties identifies the set of data libraries to associate with the RTE in the RTE definition associated with the RTE.
 3. The computer readable storage medium of claim 1, wherein the operation further comprises associating the user profile with at least a first one of the RTEs.
 4. The computer readable storage medium of claim 1, wherein the operation further comprises associating at least a first one of the RTEs with the group profile.
 5. The computer readable storage medium of claim 1, wherein the operation further comprises configuring at least a first one of the RTEs as a default RTE for executing data queries.
 6. The computer readable storage medium of claim 1, wherein the operation further comprises associating the one or more exit programs and the one or more exit program libraries with the determined RTE.
 7. A system to manage runtime environments (RTEs), the system comprising: at least one computer processor; and a memory hosting an application which, when executed on the at least one computer processor, performs an operation comprising: receiving a set of runtime environment (RTE) properties characterizing a plurality of dynamically configurable RTEs for executing data queries, wherein each of the plurality of dynamically configurable RTEs corresponds to a respective set of data libraries from a plurality of sets of data libraries, wherein each set of data libraries is distinct and stores data according to a predefined schema common across the plurality of RTEs, wherein each set of data libraries is isolated by being hosted on a respective, distinct virtual machine, wherein a respective RTE definition is generated to associate with each of the plurality of RTEs; upon receiving a query from a requesting entity logged in via a current virtual machine, dynamically determining one of the plurality of RTEs to execute the query against, wherein the RTE is determined based on a profile corresponding to the requesting entity, wherein the profile is selected from a user profile and a group profile, wherein the determined RTE is associated with one or more exit programs and one or more exit program libraries; upon determining that the system is currently configured to access the set of data libraries corresponding to a given one, of the plurality of RTEs that does not match the determined RTE, dynamically reconfiguring the system to access the set of data libraries corresponding to the determined RTE, wherein the system is dynamically reconfigured without requiring any server restart and without requiring any logging in via a different virtual machine than the current virtual machine; and prior to executing the query against the set of data libraries corresponding to the determined RTE, dynamically modifying the query using the one or more exit programs and the one or more exit program libraries associated with the determined RTE, wherein the dynamically modified query is executed against the set of data libraries corresponding to the determined RTE on the dynamically reconfigured system in order to generate a set of results that is output to the requesting entity.
 8. The system of claim 7, wherein the set of RTE properties identifies the set of one or more data libraries to associate with the RTE in the RTE definition associated with the RTE.
 9. The system of claim 7, wherein the system comprises a server computing system, wherein the application is configured to, upon determining that the server computing system is already configured for query execution according to the selected RTE definition, cause execution of the query without requiring the server computing system to be reconfigured, without requiring any server restart, and without requiring any logging in via a different virtual machine than the current virtual machine.
 10. The system of claim 9, wherein the query is modified: (i) to become a case insensitive search and (ii) to track data from set of data libraries accessed by the submitting entity, wherein the set of RTE properties identifies the set of data libraries to associate with the RTE in the RTE definition associated with the RTE.
 11. The system of claim 10, wherein the operation further comprises: associating the user profile with the determined RTE; associating the determined RTE with a group profile; configuring the determined RTE as a default RTE for executing data queries; and associating the one or more exit programs and the one or more exit program libraries with the determined RTE.
 12. The system of claim 11, wherein the application comprises a web query application operatively connected to a runtime environment of a web browser, wherein the RTE is automatically selected based on the user profile and the group profile, wherein the query is received from a requesting entity via the runtime environment.
 13. The system of claim 12, wherein the operation further comprises: generating a report from the set of results obtained from executing the query; and transmitting the report to the requesting entity.
 14. The system of claim 13, wherein the one or more exit programs are invoked by the web query application in order to modify the query, wherein each RTE definition is modifiable via an RTE configuration component; wherein the one or more exit program libraries are accessible only by the one or more exit programs, wherein the web query application is operatively connected to a database management system for a database storing the set of data libraries for the determined RTE.
 15. The system of claim 14, wherein the web query application, the database management system, the web browser, the one or more exit programs, and the RTE configuration component are distinct applications; wherein the web query application is configured to access a specified set of tables stored in the database, the specified set of tables including an RTE user table, an active RTE user table, and an RTE definition table.
 16. The system of claim 15, wherein the user RTE table includes: (i) an RTE identifier field and (ii) an RTE username field.
 17. The system of claim 16, wherein the active RTE user table includes: (i) an RTE identifier field and (ii) an RTE username field.
 18. The system of claim 17, wherein the RTE definition table includes: (i) an RTE identifier field; (ii) an RTE username field; (iii) an RTE description field; (iv) an RTE libraries field; (v) an RTE exit program field; and (vi) an RTE exit program library field.
 19. The system of claim 7, wherein the operation further comprises associating at least a first one of the RTEs with the group profile.
 20. The system of claim 7, wherein the operation further comprises configuring at least a first one of the RTEs as a default RTE for executing data queries. 